Fix OpenClaw pluginApi compatibility drift in capabilities metadata#416
Fix OpenClaw pluginApi compatibility drift in capabilities metadata#416plind-junior with Copilot wants to merge 2 commits into
Conversation
|
@coderabbitai resolve |
✅ Action performedComments resolved. Approval is disabled; enable |
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
Warning Review limit reached
Next review available in: 57 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (7)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
The failing
ci / test (py3.13)job was caused by drift between the OpenClaw plugin manifest and thekb.capabilitiesresponse. The manifest was missingopenclaw.compat.pluginApi, and capabilities did not advertise the correspondinghost_compat.openclaw.pluginApientry expected by the compatibility checks.OpenClaw compatibility metadata
openclaw.compat.pluginApitoopenclaw.plugin.jsonpackage.jsonCapabilities surface
Capabilitieswithhost_compathost_compat.openclaw.pluginApifromsrc/vouch/capabilities.pyDrift checks
tests/test_capabilities.pyfor the newhost_compatcontracttests/test_openclaw_plugin_manifest.pyto assert manifest/package compatibility parityopenclawas a dead manifest field now that it is part of the current contractSchema/docs alignment
host_compattoschemas/capabilities.schema.jsonCLAUDE.mdto document that the manifest also carries the OpenClaw compatibility floor{ "openclaw": { "compat": { "pluginApi": ">=2026.6.0" } } }